<?php
/**
 * <https://y.st./>
 * Copyright © 2016 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'title' => $a['IRC'],
	'body' => <<<END
<p>
	I&apos;ve come to the conclusion that my obsession with short names is counterproductive to setting up an $a[IRC] network for several reasons.
	First and foremost, I need allies more than I need a great name.
	<a href="http://zdasgqu3geo7i7yj.onion/">The Unknown Man</a> and I seem to agree on a lot of things as to how the network should be run.
	If I can play my strengths and he his, we should have a better chance of success than either of us would alone.
	The Unknown Man beat me to being prepared, so if that means that he gets to pick a cool-sounding name instead of me getting to pick a single-character name, that seems more than fair.
	Furthermore, my obsession with short names makes no sense, given the current context.
	When dealing with domain names, there is a length limit.
	Simply put, a short domain name technically has more subdomains than a long domain name.
	In practice, this does not mean a whole lot, as even the longest possible second- or even third-level domains has many more times the number of subdomains than there exist $a[IPv4] and $a[IPv6] addresses combined.
	If you have a domain, there may not be enough disk space or computing power in the world to host unique content and/or services at every one of your subdomains, assuming that you do not host something such as a dynamic Web page that generates content based on the domain name used to access the page.
	However, I find the extended range of subdomains to be rather symbolic of the open possibilities, possibilities that I&apos;d be cutting myself off from by insisting on using such a short network name.
	Besides, network names do not have &quot;sub-names&quot;.
	Only the single name would be used, and only really in $a[URI]s.
	As $a[URI]s do not seem to suffer from a length limit, as I said above, my obsession is out of context here.
	And that is not to mention the fact that the $a[URI] that makes use of the short name would only really work if we actually became known by our official name of &quot;s&quot;.
	More likely, if our address even gets bundled in $a[IRC] clients at all, we would become known as &quot;s network&quot;, &quot;s-net&quot;, or something else that is not just a single letter.
	The name &quot;V0rtex&quot; sounds much better, is easier to recognize, is more likely to catch on, and is more likely to lead us to actually becoming a major network.
	There is little change that we actually <strong>*will*</strong> become a major network, but I should not be imposing strange restrictions that do nothing but hinder our chances.
</p>
<p>
	Speaking of strange restrictions, I am going to try to convince The Unknown Man that we should keep our ports 994 and 6667 open to users if at all possible.
	He wants to rent server resource, so I don&apos;t know if the hosting company will allow use of port 994 to begin with.
	Furthermore, they use one of the $a[BSD] systems, I forget which one, so the things I learned about making it work on that system may not apply, even if the hosting company allows it.
	I will say this: it is a good thing that I chose to use $a[ngIRCd] yesterday, as that is the daemon that The Unknown Man and I had discussed using before.
	If it wasn&apos;t, I would need to uninstall it and set up the other daemon.
</p>
<p>
	I set up the onion ports 6697 and 9999 to forward to local port 994, so now TLS connections are available on all three ports.
</p>
<p>
	I found that my school email account comes with a $a[SIP] account.
	Of course, this account cannot be trusted because it is hosted and run by Microsoft, but maybe it means that the school is willing to contact and be contacted via $a[SIP].
	I haven&apos;t seen a $a[SIP] address on their website, so probably not, but it is worth asking about if I end up going to school there.
	When I find the time, I need to get my own $a[SIP] account set up under my own domain.
</p>
END
);
